Run Time Services

The run time engine is the heart of the application on the server, performing all tasks related to the application with the exception of batched tasks (which is run instead by the Task Engine).

The run time services settings provide some control over how requests are processed and handled. Settings can be set for the entire platform or by each run time engine server in a multi-server deployment. In a multi-server deployment, each server will appear in the list going down the page.

Adjusting these settings per run time engine instance, admins can better control performance and resource allocation. This is especially true when hardware is not identical across all run time engines.

Settings

  • General Track Timeout - this governs the amount of time the a general thread should wait to process a job before timing out.
  • Query Track Timeout - this governs the amount of time a query thread should wait to process a query job before timing out.
  • Request Network Timeout - this governs the amount of time to wait for network requests. Increase this value on very slow networks. If there is a timeout, the request goes back to client for a re-request sequence.
  • Request Cache Timeout - this governs the amount of time the response cache is held while waiting for repeat requests from the client on very slow networks. Increase this value on very slow networks.
  • General Track Threads # - this governs the number of concurrent general threads that can be created in the run time engine. Thread thrashing - over use of threads - may decrease performance, so do not set this value excessively high.
  • Query Track Threads # - this governs the number of concurrent query threads the can be created in the run time engine. Thread thrashing - over use of threads - may decrease performance, so do not set this value excessively high.Care should also be taken to not overwhelm data sources by excessively increasing the number of concurrent queries being launched from Pyramid.